The metadata suite was pinning the exact local variable name passed to the Doctor/fix dry-run renderer. The CLI now uses a different option binding, so the assertion was failing even though the repair-first path still executed the same contract.\n\nThis narrows the source guard to the behavior that matters: the doctor command remains single-source and still forwards the Doctor/fix payload together with a dry-run flag.

Constraint: The regression test must keep protecting the repair-first doctor path without forcing a cosmetic local variable name.\nRejected: Rename the CLI variable back to singleRepoOptions | needless churn in production code for a test-only mismatch\nConfidence: high\nScope-risk: narrow\nReversibility: clean\nDirective: Keep metadata assertions focused on behavioral contracts rather than ephemeral local identifier names.\nTested: node --test test/metadata.test.js\nTested: node --test test/merge-workflow.test.js\nTested: node --check bin/multiagent-safety.js\nNot-tested: full npm test suite